gtpp attribute { camel-info | cell-plmn-id | diagnostics | duration-ms | imei | local-record-sequence-number | msisdn | node-id-suffix STRING | plmn-id | rat | record-extensions rat | served-pdp-pdn-address-extension | sms { destination-number | recording-entity | service-centre } } +
Disables the specified optional field so that the information will not be present in generated CDRs.
|
•
|
26 - For GGSN: if the GGSN sends “delete PDP context request” for any other reason (e.g., the operator types “clear subscribers” on the GGSN). For SGSN: The SGSN includes this cause code in the S-CDR to indicate that a secondary PDP context activation request or a PDP context modification request has been rejected due to insufficient resources.
|
|
•
|
36 - For GGSN: this cause code is sent in the G-CDR to indicate the PDP context has been deactivated in the GGSN due to the SGSN having sent a “delete PDP context request” to the GGSN. For SGSN, this cause code is used to indicate a regular MS or network-initiated PDP context deactivation.
|
|
•
|
37 - when the network initiates a QoS modification, the SGSN sends in the S-CDR to indicate that the MS initiation deactivate request message has been rejected with QoS not accepted as the cause.
|
|
•
|
38 - if the GGSN sends “delete PDP context request” due to GTP-C/GTP-U echo timeout with SGSN. If the SGSN sends this cause code, it indicates PDP context has been deactivated due to path failure, specifically GTP-C/GTP-U echo timeout.
|
|
•
|
39 - SGSN only - this code indicates the network (GGSN) has requested a PDP context reactivation after a GGSN restart.
|
|
•
|
40 - if the GGSN sends “delete PDP context request” due to receiving a RADIUS Disconnect-Request message.
|
Important: If this keyword is enabled and the gtpp centralized-lrsn-creation option is enabled with the gtpp single-source centralized-lrsn command, then the Node ID format changes as follows. <1-byte-AAAproxy-restart-counter> <3-byte AAAproxy instance number> <node-id-suffix> If “centralized-lrsn-creation” is not enabled, then node-id format for CDRs generated by Sessmgr is as follows. <1-byte Sessmgr restart-value> <3-byte Sessmgr instance number> <node-id-suffix> If “centralized-lrsn-creation” is not enabled, then node-id format for CDRs generated by ACSMGR is as follows. <1-byte ACSmgr restart-value> <3-byte ACSmgr instance number> <Active charging service-name>node-id-suffix STRING
STRING: This is the configured Node-ID-Suffix having any string between 1 to16 characters.
Important: The NodeID field is a printable string of the ndddSTRING format: n: The first digit is the Sessmgr restart counter having a value between 0 and 7. ddd: The number of sessmgr instances. Uses the specified NodeID-suffix in all CDRs. The “Node-ID” field consists of sessMgr Recovery counter (1 digit) n + AAA Manager identifier (3 digits) ddd + the configured Node-Id-suffix (1 to 16 characters) STRING. If the centralized LRSN feature is enabled, the “Node-ID” field will consist of only the specified NodeID-suffix (NodeID-prefix is not included). If this option is not configured, then GTPP group name will be used instead (For default GTPP groups, context-name will be used).
Important: If this node-id-suffix is not configured, the GGSN uses the GTPP context name as the Node-id-suffix (truncated to 16 characters) and the SGSN uses the GTPP group named as the node-id-suffix.unknown-use hex_num: must be a hexadecimal number from 0x0 through 0xFFFFFF to identify a foreign SGSN that has not provided a PLMN-id. For GGSN only.
destination-number - Entering this option includes the "destinationNumber" field in the SMS-MO-CDR or SMS-MT-CDR.
recording-entity - Entering this option includes the "recordingEntity" field in the SMS-MO-CDR or SMS-MT-CDR.
service-centre - Entering this option includes the "serviceCentre" field in the SMS-MO-CDR or SMS-MT-CDR.
address ip_address
ip_address must be configured using dotted decimal notation.
port port
It is an optional parameter. It specifies the Charging Agent UDP port. If port is not defined, the IP will take the default port number 49999.
port must be followed by an integer, ranging from 1 to 65535.
Important: Configuring GTPP charging-agent on port 3386 may interfere with ggsn-service configured with the same ip address.This command can be used to establish a UDP interface to connect to the GSS or this command can establish a Ga interface to connect to the CFG. These interfaces must exist in the same context in which GTPP functionality is configured (refer to the gtpp commands in this chapter).
The following command configures the system to use the interface with an IP address of 192.168.13.10 as the accounting interface with port 20000 to the CGF:
gtpp charging-agent address 192.168.13.10
|
•
|
0: Designates the start sequence number as 0.
|
|
•
|
1: Designates the start sequence number as 1.
|
gtpp deadtime time
time is measured in seconds and can be configured to any integer value from 1 to 65535.
Refer to the gtpp detect-dead-server and gtpp max-retries commands for additional information on the process the system uses to mark a CGF as down.
For the GGSN: This command works in conjunction with the gtpp detect-dead-server to set an action when a communication failure is detected between the GGSN and a configured GTPP server. It disables the archiving of CDRs on the system when the GTPP server is unreachable or dead.
For the GGSN and the SGSN: Typically, duing a communication or server failure, the GGSN or SGSN retains the GTPP requests until the system buffer runs out of resources. This command enables suppression of the CDRs, so with this command the GGSN or the SGSN will start purging all CDRs associated with this GTPP group as soon as the GGSN/SGSN detects that the GTPP server is down or that a communication failure has occurred. The CDRs generated, for the period while the server is down/unreachable, will also be purged.
gtpp detect-dead-server consecutive-failures max_number
consecutive-failures max_number
Specifies the number of failures that could occur before marking a CGF as down. If 0 (zero) is the value entered, then the system will mark the CGF as dead after a single instance of max-retries has been attempted with no success, regardless of configured deadtime.
max_number could be configured to any integer value from 0 to 1000.
This command works in conjunction with the gtpp max-retries parameter to set a limit to the number of communication failures that can occur with a configured CGF.
The gtpp max-retries parameter limits the number of attempts to communicate with a CGF. Once that limit is reached, the system treats it as a single failure. The gtpp detect-dead-server parameter limits the number of consecutive failures that can occur before the system marks the CGF as down and communicate with the CGF of next highest priority.
Refer to the gtpp max-retries command for additional information.
|
•
|
custom31: Custom-defined dictionary for S-CDR encoding. Includes a field appended for PLMN-ID.
|
|
•
|
custom33: Custom-defined dictionary for S-CDR encoding. Includes a field appended for PLMN-ID and does not support diagnostic or SGSN-change fields.
|
gtpp duplicate-hold-time minutes minutes
When the primary CGF is down, the number of minutes to hold onto CDRs that may be duplicates. minutes must be an integer from 1 to 10080. Default is 60.
gtpp echo-interval time
time must be an integer from 60 to 3600. Default: 60
|
•
|
Upon the configuration of a new CGF server on the system using the gtpp server command as described in this chapter
|
|
•
|
Upon the execution of the gtpp test accounting command as described in the Exec Mode Commands chapter of this reference
|
|
•
|
Upon the execution of the gtpp sequence-numbers private-extensions command as described in this chapter
|
The echo-interval command is used in conjunction with the gtpp max-retries and gtpp timeout commands as described in this chapter.
The alive/dead status of the CGFs is used by the AAA Managers to affect the sending of CDRs to the CGFs. If all CGFs are dead, the AAA Managers will still send CDRs, (refer to the gtpp deadtime command), albeit at a slower rate than if a CGF were alive. Also, AAA Managers independently determine if CGFs are alive/dead.
gtpp egcdr { final-record [ [ include-content-ids { all | only-with-traffic } ] [ closing-cause { same-in-all-partials | unique } ] ] | losdv-max-containers max_losdv_containers | lotdv-max-containers max_lotdv_containers | service-data-flow threshold { interval interval | volume { downlink bytes [ uplink bytes ] | total bytes | uplink bytes [ downlink bytes ] } } | service-idle-timeout { 0 | service_idle_timeout } }
|
•
|
include-content-ids: Controls which content-ids are being included in the final eG-CDR.
|
|
•
|
all: Specifies that all content-ids be included in the final eG-CDR.
|
|
•
|
only-with-traffic: Specifies that only content-ids with traffic be included in the final eG-CDRs.
|
|
•
|
closing-cause: Configures closing cause for the final eG-CDR.
|
|
•
|
same-in-all-partials: Specifies that the same closing cause is to be included for multiple final eG-CDRs.
|
|
•
|
unique: Specifies that the closing cause for final eG-CDRs is to be unique.
|
losdv-max-containers max_losdv_containers
max_losdv_containers must be an integer from 1 through 255.
lotdv-max-containers max_lotdv_containers
max_lotdv_containers must be an integer from 1 through 8.
service-data-flow threshold { interval interval | volume { downlink bytes [ uplink bytes ] | total bytes | uplink bytes [ downlink bytes ] } }
|
•
|
interval interval: Specifies the time interval, in seconds, to close the eG-CDR if the minimum time duration thresholds for service data flow containers satisfied in flow-based charging.
|
interval must be an integer from 60 through 40000000.
|
•
|
volume { downlink bytes [ uplink bytes ] | total bytes | uplink bytes [ downlink bytes ] }: Specifies the volume octet counts for the generation of the interim eG-CDRs to service data flow container in FBC.
|
|
•
|
downlink bytes: Specifies the limit for the number of downlink octets after which the eG-CDR is closed.
|
|
•
|
total bytes: Specifies the limit for the total number of octets (uplink+downlink) after which the eG-CDR is closed.
|
|
•
|
uplink bytes: Specifies the limit for the number of uplink octets after which the eG-CDR is closed.
|
|
•
|
bytes must be an integer from 10000 through 400000000.
|
0: Specifies there is no service-idle-timeout trigger.
service_idle_timeout must be an integer from 10 through 86,400.
Resets the system’s configuration to the default value for error-response. Default is retry-request.
max_cdrsmust be an integer from 1 through 255.
wait-timewait_time
Configures the number of seconds the GSN waits to send the packet while accumulating CDRs as defined by max-cdr. If the wait-time interval expires before max-cdrs is reached, then this keyword over-rides and the packet is sent.
wait_time must be an integer from 1 through 300.
Important: wait-time interval can only be enabled if the value for max-cdrs max_cdrs is greater than 1.The system places CDRs into a packet until either max-cdrs is met, wait-time times out, or the maximum PDU size, configured by the gtpp max-pdu-size command, is met.
Important: This command’s configuration is ignored if CDRs are stored on an SMC hard disk.gtpp max-pdu-size pdu_size
Resets the default max-pdu-size of 4096.
pdu_size is measured in octets and can be configured to any integer value from 1024 to 65400.
Important: The maximum size of an IPv4 PDU (including the IPv4 and subsequent headers) is 65,535. However, a slightly smaller limit is imposed by this command because the system’s max-pdu-size doesn't include the IPv4 and UDP headers, and because the system may need to encapsulate GTPP packets in a different/larger IP packet (for sending to a backup device).gtpp max-pdu-size 2048
gtpp max-retries max_attempts
Resets the systems max-retries to the default of 4.
max_attempts can be configured to any integer value from 1 to 15.
This command works in conjunction with the gtpp detect-dead-server and gtpp timeout parameters to set a limit to the number of communication failures that can occur with a configured CGF.
When the value specified by this parameter is met, a failure is logged. The gtpp detect-dead-server parameter specifies the number of consecutive failures that could occur before the server is marked as down.
In addition, the gtpp timeout command controls the amount of time between re-tries.
gtpp mbms buckets number
buckets number
number can be configured to any integer value from 1 through 4.
The following command configures the bucket-based trigger to generate G-MBMS-CDRs after changes in 2 container:
gtpp mbms interval duration_sec
interval duration_sec
duration_sec is measured in seconds and can be configured to any integer value from 60 through 40,000,000.
The following command configures the interval-based trigger to generate G-MBMS-CDRs in every 60 seconds:
Important: The system assumes that the billing system uses the day/date to determine if the statistics container represents an actual tariff period.|
•
|
mins: The minutes of the hour, an integer value from 0 through 59.
|
|
•
|
hours: The hour of the day, an integer value from 0 through 23.
|
gtpp mbms tariff time1 30 11
gtpp mbms volume download_bytes
volume download_bytes
download_bytes is the total download traffic volume measured in octets and can be configured to any integer value from 100,000 through 4,000,000,000.
gtpp mbms volume download_bytes
Configures the system to allow/disallow the redirection of CDRs when the primary CGF is unavailable.
This command allows operators to better handle erratic network links, without having to remove the configuration of the backup server(s) via the no gtpp server command.
If the no gtpp redirection-allowed command is executed, the system only sends CDRs to the primary CGF. If that CGF goes down, the system will buffer the CDRs in memory until the CGF comes back or until the system runs out of buffer memory. In addition, if the primary CGF announces its intent to go down (with a GTPP Redirection Request message), the system responds to that request with an error response.
This command has been obsoleted and is replaced by the gtpp redirection-allowed command.
gtpp server ip_address [ max msgs ] [ priority priority ] [ udp-port port ] [ node-alive { enable | disable } ] [ -noconfirm ]
max msgs
msgs can be configured to any integer value from 1 to 256.
prioritypriority
priority can be configured to any integer value from 1 to 1000. When configuring two or more servers with the same priority you will be asked to confirm that you want to do this. If you use the -noconfirm option, you are not asked for confirmation and multiple servers could be assigned the same priority.
udp-portport
Specifies the UDP port over which the GGSN communicates with the CGF. port can be configured to any integer value between 1 and 65535.
Important: The configuration of multiple CGFs with the same IP address but different port numbers is not supported.no gtpp server 100.10.35.7
port port_num
gtpp storage-server 192.168.1.2
gtpp storage-server local file { compression { gzip | none } | format { custom1 | custom2 | custom3 | custom4 | custom5 | custom6 | custom7 | custom8 } | name { format string [ max-file-seq-num seq_number ] | prefix prefix } | purge-processed-files [ file-name-pattern name_pattern | purge-interval purge_interval ] | rotation { cdr-count count | time-interval time [ force-file-rotation ] | volume mb size } | start-file-seq-num seq_num [ recover-file-seq-num }
default gtpp storage-server local file { compression | format | name { format | prefix } | purge-processed-files | rotation { cdr-count | time-interval | volume } start-file-seq-num }
no gtpp storage-server local file { purge-processed-files | rotation { cdr-count | time-interval } }
gzip — Enables Gzip file compression.
none — Disables Gzip file compression -this is the default value.
custom1 — File format custom1 - this is the default file format.
custom2 to custom5 Customer specific CDR file formats.
custom6 — File format custom6 with a block size of 8K for CDR files.
custom7 — File format custom7 is a customer specific CDR file formate.
custom8 — File format custom8 is a customer specific CDR file format. It uses node-id-suffix_date_time_fixed-length-seq-num.u format for file naming where:
|
•
|
date is date in MMDDYYYYY (01312010) for mat
|
|
•
|
time is time in HHMMSS (023508) format
|
|
•
|
fixed-length-seq-num is the fixed length of srquence number for specific file having 6 digit counter starting from 000001 and end to 999999. Once file sequence reached to 999999 the sequence will be reset to 000001.
|
name format string
string — Enter a string of 1 to 127 alphanumeric characters. The string must begin with the % (percent sign).
|
•
|
%y: = year as a decimal number without century (range 00 to 99).
|
|
•
|
%Y: = year as a decimal number with century.
|
|
•
|
%m: = month as a decimal number (range 01 to 12).
|
|
•
|
%d: = day of the month as a decimal number (range 01 to 31).
|
|
•
|
%H: = hour as a decimal number 24-hour format (range 00 to 23).
|
|
•
|
%h: = hour as a decimal number 12-hour format (range 01 to 12).
|
|
•
|
%M: = minute as a decimal number (range 00 to 59).
|
|
•
|
%S: = second as a decimal number (range 00 to 60). (The range is up to 60 to allow occasional leap seconds.)
|
|
•
|
%Q: = File sequence number. Field width may be specified between the % and the Q .If the natural size of the field is smaller than this width, then the result string is padded (on the left) to the specified width with 0s
|
|
•
|
%N: = No of CDRs in the file. Field width may be specified between the % and the N .If the natural size of the field is smaller than this width, then the result string is padded (on the left) to the specified width with 0s
|
|
•
|
%%: = This field is used to add % to the CDR file name.
|
|
•
|
max-file-seq-no: This can be configured optionally. It indicates the maximum value of sequence number in file name (starts from 1). Once the configured max-file-seq-no limit is reached, the sequence number will restart from 1. If no max-file-seq-no is specified then file sequence number ranges from 1- 4294967295.
|
name prefix prefix
prefix — Enter a string of 1 to 64 alphanumeric characters or do not enter a value (NULL).
Important: This option is available only when GTPP server storage mode is configured for local storage of CDRs with the gtpp storage-server mode local command and the purge-processed-files parameters is enabled.file-name-pattern name_pattern defines a pattern for the file name that will be used to match against the files to be purged. This means that the only files to be selected and deleted will be those with names matching this pattern and whose age (when to purge) has been specified with the existing purge-interval parameter.
name_pattern enter a string up to 127 characters in length that can contain ‘*’ (wild card to match 0+ chars) and one or more ‘:’ (to specify alternate, synonymous with ‘|’); for example: file-name-pattern “*.P:*.dat” matches “anything.P” AND “anything.dat”
purge-interval purge_interval provides an option for user to control the purge interval duration in minutes by setting purge_interval.
purge_interval must be an integer from 1 through 259200.
cdr-count count - Configure the CDR count for the file rotation. Enter a value from 1000 to 65000. Default value 10000.
time-interval time - Configure the time interval for file rotation. Enter a value in seconds ranging from 30 to 86400. Default value is 3600 seconds (1 hour).
force-file-rotation - Force CDR file-rotation at specified interval, configured with time-interval time keyword, even if there are no CDRs generated. By default this keyword is “Disbaled”.
volume size — Configure the file volume, in MB, for file rotation. Enter a value ranging from 2 to 40. This trigger can not be disabled. Default value is 10MB.
Using this keyword enables the continuous file sequence number function. start-file-seq-num specifies the lowest number to be used as a file sequence number in the case of aaaproxy or chassis restart/reboot.
seq_num must be an integer from 1 to 4294967295. Entering a value of 1, disables the recover file sequence number function. Entering any other number, for example 10, would instruct the SGSN to always start from 10 as the file sequence number in the event that the aaaproxy or chassis reload.
When files are moved, the file sequence numbers are synched and stored in both RAM and the hard disk drive (HDD). recover-file-seq-num instructs the SGSN to recover the last (largest) stored file sequence number, in the event that the aaaproxy/chassis restart/reboot, to continue file sequence numbering rather than resetting the file sequence numbering to the lowest start file sequence number.
gtpp storage-server max-retries max_attempts
max_attempts can be configured to any integer value from 1 to 15.
This command works in conjunction with the gtpp storage-server timeout parameters to set a limit to the number of communication failures that can occur with a configured GTPP back-up storage server.
The gtpp storage-server timeout command controls the amount of time between re-tries.
Refer to the gtpp storage-server timeout command for additional information.
Returns the GTPP group configuration to the default ‘remote’ value for the GTPP storage server mode.
Important: This option is available with ASR 5000 platforms only.
Important: When the external server is down, the Session Managers will start buffering up to a maximum of 26400 CDRs or a total of 120 MB worth of CDRs, whichever limit reaches first. The maximum CDR limit specified is per the session manager. The chassis level limit varies depending on the number of session manager instances and number of active cards.
Important: This option is available with ASR 5000 platforms only.gtpp storage-server timeout duration
duration is measured in seconds and can be configured to any integer value from 30 to 120.
This command works in conjunction with the gtpp storage-server max-retries command to establish a limit on the number of times that communication with a GTPP back-up storage server is attempted before a failure is logged.
gtpp timeout time
time is measured in seconds and can be configured to any integer value from 1 to 60.
This command works in conjunction with the gtpp max-retries command to establish a limit on the number of times that communication with a CGF is attempted before a failure is logged.
gtpp timeout 30
Enables the cell update trigger for S-CDRs, if the dictionary specified in the gtpp dictionary configuration includes support for cell update. This trigger is available only for 2G. Currently, custom18 dictionary supports the cell update trigger.
Enables the PLMNID change trigger for S-CDRs if the dictionary specified in the gtpp dictionary configuration supports the PLMNID change. If enabled, the SGSN generates a partial S-CDR when the MS changes the PLMN while under the same SGSN (intra-system intra-SGSN PLMN-ID handover). Currently, custom18 dictionary supports this trigger.
After the RAT change, the System Type field in CDR changes to indicate the new system type. If this trigger is disabled, then the next CDR generated will indicate System Type, but the data count in the CDR does not necessarily belong to the system type indicated in CDR; instead, it may belong to both 2G and 3G as CDR is not closing when handover takes place.
Important: System Type field in CDR-related change is not applicable to customized CDR formats, which does not use System Type fieldgenerate: Choice of generation of CDR or just a Container on a RAT change.
cdr: Generates a CDR on a RAT-change.
container: Generates a Container only on a RAT-change.
This keyword is obsolete and is available to maintain the backward compatibility for existing customers. The new keyword for sgsn-change-limit is serving-node-change-limit.
also-intra-sgsn-multiple-address-group-change: This keyword includes Intra-SGSN group changes as an SGSN change.
This keyword is enabled for PGW, SGW, and GGSN. However, the also-intra-sgsn-multiple-address-group-change is enabled only for GGSN.
also-intra-sgsn-multiple-address-group-change : This keyword includes Intra-SGSN group changes as an SGSN change.
